Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 934724f84ec835c4397dc0fe127546303f01156c76e1c91392545cf2660f40a7

Tx prefix hash: 3b791cb3cf482cead3436bcd2082c2a58899a56e7be1bc4d704c6c8215518c94
Tx public key: 4f59be9904b6ca6bae2e6458dc85f37d91faf1e095dc7691be4833f6943b8ec1
Timestamp: 1741206994 Timestamp [UCT]: 2025-03-05 20:36:34 Age [y:d:h:m:s]: 00:260:07:51:30
Block: 1232909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183791 RingCT/type: yes/0
Extra: 014f59be9904b6ca6bae2e6458dc85f37d91faf1e095dc7691be4833f6943b8ec102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8f1e245b68228229dab6d253e3b4fb4054e12369cedbfe43aabe96b7f78738f 0.600000000000 1719826 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": 1232919, "vin": [ { "gen": { "height": 1232909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8f1e245b68228229dab6d253e3b4fb4054e12369cedbfe43aabe96b7f78738f" } } ], "extra": [ 1, 79, 89, 190, 153, 4, 182, 202, 107, 174, 46, 100, 88, 220, 133, 243, 125, 145, 250, 241, 224, 149, 220, 118, 145, 190, 72, 51, 246, 148, 59, 142, 193, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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