Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01639782c57b06233d7b117b1e1b9a610ac23f5376a30f3305bdd120d4585d96

Tx prefix hash: 46846e14e2b1a7f61d8e83c7a32def2113cfaaa8ab043dcd660494895c26c32f
Tx public key: 06c7a5abf622f99662c3b4079ee20ac191a549bf12ca22a2369dae17844c2838
Timestamp: 1671390219 Timestamp [UCT]: 2022-12-18 19:03:39 Age [y:d:h:m:s]: 01:350:04:49:53
Block: 655446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511306 RingCT/type: yes/0
Extra: 0106c7a5abf622f99662c3b4079ee20ac191a549bf12ca22a2369dae17844c28380211000000027e406890000000000000000000

1 output(s) for total of 4.132713434000 dcy

stealth address amount amount idx
00: 3c0a5879f85a1c4adc1549ea3a4dd60626a5cb04f84bb0093c7f2c9c4994eb9f 4.132713434000 1096003 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": 655456, "vin": [ { "gen": { "height": 655446 } } ], "vout": [ { "amount": 4132713434, "target": { "key": "3c0a5879f85a1c4adc1549ea3a4dd60626a5cb04f84bb0093c7f2c9c4994eb9f" } } ], "extra": [ 1, 6, 199, 165, 171, 246, 34, 249, 150, 98, 195, 180, 7, 158, 226, 10, 193, 145, 165, 73, 191, 18, 202, 34, 162, 54, 157, 174, 23, 132, 76, 40, 56, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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