Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1121ad06701a30e22e1679d9bb175b463c0f761b7f5f9131d16aaa7f61a00780

Tx prefix hash: 577686955eac0b246d173ef0661f78517f7aea0fdf6b32f12f24393b0aad9c4f
Tx public key: 736eddbe1b2dc1ac5e809f972fbd4a607d9b864d9bb4cfc82df7544847913a93
Timestamp: 1748921827 Timestamp [UCT]: 2025-06-03 03:37:07 Age [y:d:h:m:s]: 00:161:16:57:30
Block: 1296787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113249 RingCT/type: yes/0
Extra: 01736eddbe1b2dc1ac5e809f972fbd4a607d9b864d9bb4cfc82df7544847913a9302110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffa60a9b008041ffb301861c8e22da8226dd1387399f17d5378611fab215c2c4 0.600000000000 1784304 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1296797, "vin": [ { "gen": { "height": 1296787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffa60a9b008041ffb301861c8e22da8226dd1387399f17d5378611fab215c2c4" } } ], "extra": [ 1, 115, 110, 221, 190, 27, 45, 193, 172, 94, 128, 159, 151, 47, 189, 74, 96, 125, 155, 134, 77, 155, 180, 207, 200, 45, 247, 84, 72, 71, 145, 58, 147, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8