Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5dfb84d5d105b0aa72deee18f95d274080a5bfa8257bcfba97bbc6be34d480

Tx prefix hash: be4e4da9109d95fc314cdc2f3278001078aed58457dc43e8dddbb222def878ba
Tx public key: 96f82c8dae1f000fd3026268c8931f8c3d4c90cf07c3075e03c1dc88078afcc7
Timestamp: 1728401102 Timestamp [UCT]: 2024-10-08 15:25:02 Age [y:d:h:m:s]: 01:037:21:34:59
Block: 1127210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285461 RingCT/type: yes/0
Extra: 0196f82c8dae1f000fd3026268c8931f8c3d4c90cf07c3075e03c1dc88078afcc7021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a351ddc924f6833e4f245a2b709d18c106ab95ec2ab74a4f70cf18d1335befbb 0.600000000000 1610011 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": 1127220, "vin": [ { "gen": { "height": 1127210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a351ddc924f6833e4f245a2b709d18c106ab95ec2ab74a4f70cf18d1335befbb" } } ], "extra": [ 1, 150, 248, 44, 141, 174, 31, 0, 15, 211, 2, 98, 104, 200, 147, 31, 140, 61, 76, 144, 207, 7, 195, 7, 94, 3, 193, 220, 136, 7, 138, 252, 199, 2, 17, 0, 0, 0, 2, 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