Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9db26501d6513270cf06f9acdb998352f243a1313be853bf37b5c3427b589c79

Tx prefix hash: 5bda6a07b1e0d00d630dd55dcf07d08aa59a9429481d923bb5a1554eea732bfd
Tx public key: 230c22ec4dc74bbb58cc3e2f34f08b53c41cc68ca3bfd58628180f23b590e0eb
Timestamp: 1723371239 Timestamp [UCT]: 2024-08-11 10:13:59 Age [y:d:h:m:s]: 00:298:21:17:53
Block: 1085509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213545 RingCT/type: yes/0
Extra: 01230c22ec4dc74bbb58cc3e2f34f08b53c41cc68ca3bfd58628180f23b590e0eb021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8123037b10bccb775e4b9f331924c061e2fd687aa0c32ee9abf261d3b4fadf4 0.600000000000 1560096 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": 1085519, "vin": [ { "gen": { "height": 1085509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8123037b10bccb775e4b9f331924c061e2fd687aa0c32ee9abf261d3b4fadf4" } } ], "extra": [ 1, 35, 12, 34, 236, 77, 199, 75, 187, 88, 204, 62, 47, 52, 240, 139, 83, 196, 28, 198, 140, 163, 191, 213, 134, 40, 24, 15, 35, 181, 144, 224, 235, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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