Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 911130818ffed14d7ab30621e50c826a169cca27f6f4e603cdd567d49cb032d3

Tx prefix hash: 109e72b47144454d38597c6a8e1114e3576020304e342c340a1a3dde8ead7b37
Tx public key: a2a4acf35f72c9ac0f35c3a8bacd8be58dac7c762f41fe4f60d7f471e70f4618
Timestamp: 1725660333 Timestamp [UCT]: 2024-09-06 22:05:33 Age [y:d:h:m:s]: 00:286:03:26:30
Block: 1104487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204248 RingCT/type: yes/0
Extra: 01a2a4acf35f72c9ac0f35c3a8bacd8be58dac7c762f41fe4f60d7f471e70f461802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9603428282ef95adde8ef6d07c596f2447f6bdda684a8131a9a64f91804f9509 0.600000000000 1581644 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": 1104497, "vin": [ { "gen": { "height": 1104487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9603428282ef95adde8ef6d07c596f2447f6bdda684a8131a9a64f91804f9509" } } ], "extra": [ 1, 162, 164, 172, 243, 95, 114, 201, 172, 15, 53, 195, 168, 186, 205, 139, 229, 141, 172, 124, 118, 47, 65, 254, 79, 96, 215, 244, 113, 231, 15, 70, 24, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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