Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a03be7ce7529cb5ffc88efc755a743a0aa17d01c32d4c1a9233a5e7fb92049a2

Tx prefix hash: 0c597a5fe409a5b84225211c8e90d3dc440d14ec691b28537d357e4a7c769e71
Tx public key: 890bca64db833ffbfae2d43f2f9749fba08638ce6a2fc92353b692f3ffaffe71
Timestamp: 1722745923 Timestamp [UCT]: 2024-08-04 04:32:03 Age [y:d:h:m:s]: 00:204:07:23:50
Block: 1080320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145880 RingCT/type: yes/0
Extra: 01890bca64db833ffbfae2d43f2f9749fba08638ce6a2fc92353b692f3ffaffe7102110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58146ea27772f282f19bba16e016ed9a8452d119d08ea2a855e3d35d4992e541 0.600000000000 1553623 of 15

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": 1080330, "vin": [ { "gen": { "height": 1080320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58146ea27772f282f19bba16e016ed9a8452d119d08ea2a855e3d35d4992e541" } } ], "extra": [ 1, 137, 11, 202, 100, 219, 131, 63, 251, 250, 226, 212, 63, 47, 151, 73, 251, 160, 134, 56, 206, 106, 47, 201, 35, 83, 182, 146, 243, 255, 175, 254, 113, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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