Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aa61b16113ed3ceeeb36c11c5bdb66ed9497eff0a2dd2f27eb292415f3aa159

Tx prefix hash: 01d43320c2caa0c85446cb834ff0b2cf376d02f0d8c75fa04ad2930162737fb7
Tx public key: a6e5e822a90517b6cfaa279fb1c06f96b1ff5f1c11378b74e892fe12bd42479e
Timestamp: 1666368042 Timestamp [UCT]: 2022-10-21 16:00:42 Age [y:d:h:m:s]: 02:188:00:32:50
Block: 613934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656055 RingCT/type: yes/0
Extra: 01a6e5e822a90517b6cfaa279fb1c06f96b1ff5f1c11378b74e892fe12bd42479e02110000000833af99f4000000000000000000

1 output(s) for total of 5.672595828000 dcy

stealth address amount amount idx
00: 8616a806121eeaefe378e64c32695e2075afd800abcdcbea6eb139ddd7bbbad1 5.672595828000 1051273 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": 613944, "vin": [ { "gen": { "height": 613934 } } ], "vout": [ { "amount": 5672595828, "target": { "key": "8616a806121eeaefe378e64c32695e2075afd800abcdcbea6eb139ddd7bbbad1" } } ], "extra": [ 1, 166, 229, 232, 34, 169, 5, 23, 182, 207, 170, 39, 159, 177, 192, 111, 150, 177, 255, 95, 28, 17, 55, 139, 116, 232, 146, 254, 18, 189, 66, 71, 158, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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