Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f2332607f8e6d56c42ded6a95e026ceb0b8148cf64a612866635702cd6207e

Tx prefix hash: c852841b86d6309a07638ec84d53154c1d8f41ddd65c64bac324e23325860ee8
Tx public key: 04af60c86d41681f6658fb934b81182ca72b0f32788d903435e6bae616c503df
Timestamp: 1582319455 Timestamp [UCT]: 2020-02-21 21:10:55 Age [y:d:h:m:s]: 05:277:06:50:32
Block: 69713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1349139 RingCT/type: yes/0
Extra: 0104af60c86d41681f6658fb934b81182ca72b0f32788d903435e6bae616c503df02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 360.589184076000 dcy

stealth address amount amount idx
00: 4bb4c560462cad92eb6c7cc193efb4ddf57ab0d39b2e444779b99a78a143ba93 360.589184076000 128646 of 0

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": 69723, "vin": [ { "gen": { "height": 69713 } } ], "vout": [ { "amount": 360589184076, "target": { "key": "4bb4c560462cad92eb6c7cc193efb4ddf57ab0d39b2e444779b99a78a143ba93" } } ], "extra": [ 1, 4, 175, 96, 200, 109, 65, 104, 31, 102, 88, 251, 147, 75, 129, 24, 44, 167, 43, 15, 50, 120, 141, 144, 52, 53, 230, 186, 230, 22, 197, 3, 223, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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