Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be30507a84476fb40ad8fd67dc8a8797436cd69029bf37e0ea394565c28bcbdf

Tx prefix hash: df8d4a718ed5f1e44c8533b5e167ca609462334edee03646da33deac714b345d
Tx public key: 70800f3e9dd0e1eab2be9cd11e6256cb6490cd33756f7ce7a56169b4f45d0a7f
Timestamp: 1687452399 Timestamp [UCT]: 2023-06-22 16:46:39 Age [y:d:h:m:s]: 01:289:11:58:10
Block: 787970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468054 RingCT/type: yes/0
Extra: 0170800f3e9dd0e1eab2be9cd11e6256cb6490cd33756f7ce7a56169b4f45d0a7f0211000000014b8f5122000000000000000000

1 output(s) for total of 1.503586562000 dcy

stealth address amount amount idx
00: e21ee5941c94b041e840903c2f71b9d1cbf5f3989be87cdf16a82140c7c99843 1.503586562000 1238057 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": 787980, "vin": [ { "gen": { "height": 787970 } } ], "vout": [ { "amount": 1503586562, "target": { "key": "e21ee5941c94b041e840903c2f71b9d1cbf5f3989be87cdf16a82140c7c99843" } } ], "extra": [ 1, 112, 128, 15, 62, 157, 208, 225, 234, 178, 190, 156, 209, 30, 98, 86, 203, 100, 144, 205, 51, 117, 111, 124, 231, 165, 97, 105, 180, 244, 93, 10, 127, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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