Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7dbb935d246c13dcdd197b7bb9e0461829044d444ec125736841ee74d8c54e0

Tx prefix hash: 6ad423c966d109918df59167ded846669cd4e74a701ee30d5ef78c575a559c6a
Tx public key: ad5696486a65f8ec0daae3523f27a0c6dd172d04845e460c32fc2f3584dc7464
Timestamp: 1646517902 Timestamp [UCT]: 2022-03-05 22:05:02 Age [y:d:h:m:s]: 02:355:12:49:20
Block: 452107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 773340 RingCT/type: yes/0
Extra: 01ad5696486a65f8ec0daae3523f27a0c6dd172d04845e460c32fc2f3584dc74640211000000094a0f5013000000000000000000

1 output(s) for total of 19.497642636000 dcy

stealth address amount amount idx
00: e02feaea6cb8e4a1cf7f372a53d96638c4e19ec3abc53337cf6d33a8afe2927f 19.497642636000 867346 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": 452117, "vin": [ { "gen": { "height": 452107 } } ], "vout": [ { "amount": 19497642636, "target": { "key": "e02feaea6cb8e4a1cf7f372a53d96638c4e19ec3abc53337cf6d33a8afe2927f" } } ], "extra": [ 1, 173, 86, 150, 72, 106, 101, 248, 236, 13, 170, 227, 82, 63, 39, 160, 198, 221, 23, 45, 4, 132, 94, 70, 12, 50, 252, 47, 53, 132, 220, 116, 100, 2, 17, 0, 0, 0, 9, 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