Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c24f7b737530743a06dae15b2711e25fd65d8aa40210c223b75866ba9797483f

Tx prefix hash: 78e1dcc42e15320b28222f8e93aac6573572aa2048b9f6214ecaa8a769980ed1
Tx public key: 4d2b2659b8f7bda2fdecddd504e305ef83cb207979b029f1bce4e0c75da97a1d
Timestamp: 1746823412 Timestamp [UCT]: 2025-05-09 20:43:32 Age [y:d:h:m:s]: 00:189:03:49:19
Block: 1279401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132904 RingCT/type: yes/0
Extra: 014d2b2659b8f7bda2fdecddd504e305ef83cb207979b029f1bce4e0c75da97a1d0211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd34a898b4f075fd68346b2bfa689289855622eea26b50bccf487ba92083a070 0.600000000000 1766778 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": 1279411, "vin": [ { "gen": { "height": 1279401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd34a898b4f075fd68346b2bfa689289855622eea26b50bccf487ba92083a070" } } ], "extra": [ 1, 77, 43, 38, 89, 184, 247, 189, 162, 253, 236, 221, 213, 4, 227, 5, 239, 131, 203, 32, 121, 121, 176, 41, 241, 188, 228, 224, 199, 93, 169, 122, 29, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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