Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a515f64e7f7d5a8ce9f23ec4041f770fc0d39f90cabb2b16ebdff238c49d0a4f

Tx prefix hash: 457b3a6e84e31f173d0d6860e0baa8b0f64b2444a6520977f36a1336f456a7b8
Tx public key: 49d7aa19b89efd9d9b64345581a86f68f866a711e3af1cd2c0b1213607197c5c
Timestamp: 1721414263 Timestamp [UCT]: 2024-07-19 18:37:43 Age [y:d:h:m:s]: 00:261:23:26:40
Block: 1069288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187138 RingCT/type: yes/0
Extra: 0149d7aa19b89efd9d9b64345581a86f68f866a711e3af1cd2c0b1213607197c5c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b65b0f2723f9aaa910f34104e7fd254045adf5e866b175e67876f9d8e50c0509 0.600000000000 1540657 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": 1069298, "vin": [ { "gen": { "height": 1069288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b65b0f2723f9aaa910f34104e7fd254045adf5e866b175e67876f9d8e50c0509" } } ], "extra": [ 1, 73, 215, 170, 25, 184, 158, 253, 157, 155, 100, 52, 85, 129, 168, 111, 104, 248, 102, 167, 17, 227, 175, 28, 210, 192, 177, 33, 54, 7, 25, 124, 92, 2, 17, 0, 0, 0, 6, 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