Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a35f7002248e54b3f05d90e78290e54dfbf75c1a112aa7a97348abac7b95eb

Tx prefix hash: 3491ba4a266ca972e852bc5fde819665fb0a0aae60842c14622f24c71798be8e
Tx public key: 618d4a39bd54fb09698015a845b2daa861a7f9c30016d42d7c8cb022bdfbaaa4
Timestamp: 1577826009 Timestamp [UCT]: 2019-12-31 21:00:09 Age [y:d:h:m:s]: 05:108:09:04:24
Block: 36010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227223 RingCT/type: yes/0
Extra: 01618d4a39bd54fb09698015a845b2daa861a7f9c30016d42d7c8cb022bdfbaaa40211000000738a2ee0d9000000000000000000

1 output(s) for total of 466.320786737000 dcy

stealth address amount amount idx
00: e0b5f2ffa23cadda7712a678edd47835ee3aa1416a6daef33f0aec1638809e0a 466.320786737000 60842 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": 36020, "vin": [ { "gen": { "height": 36010 } } ], "vout": [ { "amount": 466320786737, "target": { "key": "e0b5f2ffa23cadda7712a678edd47835ee3aa1416a6daef33f0aec1638809e0a" } } ], "extra": [ 1, 97, 141, 74, 57, 189, 84, 251, 9, 105, 128, 21, 168, 69, 178, 218, 168, 97, 167, 249, 195, 0, 22, 212, 45, 124, 140, 176, 34, 189, 251, 170, 164, 2, 17, 0, 0, 0, 115, 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