Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a84fb1169986d4277758de5b5f1636ac7774b1de72da3d9e5515e1b7c2dd5f

Tx prefix hash: 9e390d370fb3bbc8ddad58969f5363ee6d52925039db45b214e717b71a79bdd3
Tx public key: ed7e7dd3a6759069cd2511513c47ad2d39b96950eadfa8da53b1eb823a7b86dc
Timestamp: 1702938114 Timestamp [UCT]: 2023-12-18 22:21:54 Age [y:d:h:m:s]: 01:350:18:47:15
Block: 916101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509590 RingCT/type: yes/0
Extra: 01ed7e7dd3a6759069cd2511513c47ad2d39b96950eadfa8da53b1eb823a7b86dc021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e59e61cd69b4b903dd87a122bd0e474974e0170a6fa272b77b38be6567e7469 0.600000000000 1373577 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": 916111, "vin": [ { "gen": { "height": 916101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e59e61cd69b4b903dd87a122bd0e474974e0170a6fa272b77b38be6567e7469" } } ], "extra": [ 1, 237, 126, 125, 211, 166, 117, 144, 105, 205, 37, 17, 81, 60, 71, 173, 45, 57, 185, 105, 80, 234, 223, 168, 218, 83, 177, 235, 130, 58, 123, 134, 220, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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