Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c339b121cf575d8a899d7cfafb59fa42e95bbcc02f904b71f7b1e016f1a6dce2

Tx prefix hash: 52388a24a51888a51d376978a9bba15a3462e57b0cdd11481a63adcb2fd8acc4
Tx public key: cf0a652863604eab8f28f4891944caee95b9a2545ca0da7d9c45d013b083dd4a
Timestamp: 1644922697 Timestamp [UCT]: 2022-02-15 10:58:17 Age [y:d:h:m:s]: 02:327:20:29:00
Block: 439103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753626 RingCT/type: yes/0
Extra: 01cf0a652863604eab8f28f4891944caee95b9a2545ca0da7d9c45d013b083dd4a0211000000024da16a3a000000000000000000

1 output(s) for total of 21.531276366000 dcy

stealth address amount amount idx
00: 0b8178ba55632145b4e2612c4f3a3f59593d10e4acec386a1cf748d9f770315a 21.531276366000 851132 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": 439113, "vin": [ { "gen": { "height": 439103 } } ], "vout": [ { "amount": 21531276366, "target": { "key": "0b8178ba55632145b4e2612c4f3a3f59593d10e4acec386a1cf748d9f770315a" } } ], "extra": [ 1, 207, 10, 101, 40, 99, 96, 78, 171, 143, 40, 244, 137, 25, 68, 202, 238, 149, 185, 162, 84, 92, 160, 218, 125, 156, 69, 208, 19, 176, 131, 221, 74, 2, 17, 0, 0, 0, 2, 77, 161, 106, 58, 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