Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d099e9495c318f93d042fb76b5b1ac5d4266a686f525dd11cdc0cbce73d783ae

Tx prefix hash: 9034da5d690c72c7ead909b520bc5e9994fb2f59443902ccee8d3ac97a8c5383
Tx public key: 316108ae0a68a7487712948da9ca19c8a5a4ce34af7d84ec975aa40f431bd46f
Timestamp: 1634279261 Timestamp [UCT]: 2021-10-15 06:27:41 Age [y:d:h:m:s]: 03:193:06:57:55
Block: 353387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 915785 RingCT/type: yes/0
Extra: 01316108ae0a68a7487712948da9ca19c8a5a4ce34af7d84ec975aa40f431bd46f0211000000014a0f5013000000000000000000

1 output(s) for total of 41.407841255000 dcy

stealth address amount amount idx
00: 9c2240b8ded341ed406696aaac402605ae5ff1148caa15e61ec6176195954aec 41.407841255000 722135 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": 353397, "vin": [ { "gen": { "height": 353387 } } ], "vout": [ { "amount": 41407841255, "target": { "key": "9c2240b8ded341ed406696aaac402605ae5ff1148caa15e61ec6176195954aec" } } ], "extra": [ 1, 49, 97, 8, 174, 10, 104, 167, 72, 119, 18, 148, 141, 169, 202, 25, 200, 165, 164, 206, 52, 175, 125, 132, 236, 151, 90, 164, 15, 67, 27, 212, 111, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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