Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531b2fe6d25f4928e1210f87ae0263855c25ecf26bd6e111bbcac1101c5c200c

Tx prefix hash: f5229b2934f13f6ba9a580d9fc3eb292a6c7915d1e0a7f15c87f2a19b9388b30
Tx public key: 96a10b9a3235df7bc6239dbcea687c145dd0a439139b9f2d38b5109d864a1ec0
Timestamp: 1711544708 Timestamp [UCT]: 2024-03-27 13:05:08 Age [y:d:h:m:s]: 00:293:14:07:12
Block: 987480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210125 RingCT/type: yes/0
Extra: 0196a10b9a3235df7bc6239dbcea687c145dd0a439139b9f2d38b5109d864a1ec00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 065acc85d68d37e56feaf958d41223e0c62cf62b729274697aa8e599b2e9c8b3 0.600000000000 1447731 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": 987490, "vin": [ { "gen": { "height": 987480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "065acc85d68d37e56feaf958d41223e0c62cf62b729274697aa8e599b2e9c8b3" } } ], "extra": [ 1, 150, 161, 11, 154, 50, 53, 223, 123, 198, 35, 157, 188, 234, 104, 124, 20, 93, 208, 164, 57, 19, 155, 159, 45, 56, 181, 16, 157, 134, 74, 30, 192, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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