Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce99d0d4a7c0447f70abf6923440be050c063c6b58c8d947a13915c69ce4dd9b

Tx prefix hash: 0b1a0db520d4e47d5aaee0fd16f0211b58f7937819e5c1847239537f0cd8ec43
Tx public key: afdf32803938bd454cab81b95c9b71bad956404f97dda02aabe7648d70fad7f1
Timestamp: 1648843828 Timestamp [UCT]: 2022-04-01 20:10:28 Age [y:d:h:m:s]: 02:231:17:21:10
Block: 471142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 685274 RingCT/type: yes/0
Extra: 01afdf32803938bd454cab81b95c9b71bad956404f97dda02aabe7648d70fad7f1021100000003d3fcec30000000000000000000

1 output(s) for total of 16.862082952000 dcy

stealth address amount amount idx
00: c9ec73bacd44663233c6bf3357d4dc84ef5ea089ee9d64f3d4861b29f0f25213 16.862082952000 890426 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": 471152, "vin": [ { "gen": { "height": 471142 } } ], "vout": [ { "amount": 16862082952, "target": { "key": "c9ec73bacd44663233c6bf3357d4dc84ef5ea089ee9d64f3d4861b29f0f25213" } } ], "extra": [ 1, 175, 223, 50, 128, 57, 56, 189, 69, 76, 171, 129, 185, 92, 155, 113, 186, 217, 86, 64, 79, 151, 221, 160, 42, 171, 231, 100, 141, 112, 250, 215, 241, 2, 17, 0, 0, 0, 3, 211, 252, 236, 48, 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