Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01e51c9cc7d7df1d34a450a903a51cb10e5edf1a5e67e1b42d5456fd7592ffbf

Tx prefix hash: 0f586599a1c41006198383d938b70dba75a85c951571d2c1ee5ef603a3516828
Tx public key: 15c7eb96b999bf2e911a5726c0e8721e183ca6293d49a7ce6cf192f633456718
Timestamp: 1726598637 Timestamp [UCT]: 2024-09-17 18:43:57 Age [y:d:h:m:s]: 00:197:11:56:11
Block: 1112251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140980 RingCT/type: yes/0
Extra: 0115c7eb96b999bf2e911a5726c0e8721e183ca6293d49a7ce6cf192f63345671802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 359a52d266d3db920a0f5cdedcc9a406fa7c5f99011fab55ebe99e7cdbfdd22e 0.600000000000 1591510 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": 1112261, "vin": [ { "gen": { "height": 1112251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "359a52d266d3db920a0f5cdedcc9a406fa7c5f99011fab55ebe99e7cdbfdd22e" } } ], "extra": [ 1, 21, 199, 235, 150, 185, 153, 191, 46, 145, 26, 87, 38, 192, 232, 114, 30, 24, 60, 166, 41, 61, 73, 167, 206, 108, 241, 146, 246, 51, 69, 103, 24, 2, 17, 0, 0, 0, 8, 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