Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e090edddee758625f97635a73257c980bb7b4ffb1fdc5edd756a9ed8e68d32b

Tx prefix hash: ea68d45a7cf28d4fc87ee7271a5e353c1614e0d91f41d5a603497a96d903f27d
Tx public key: 3fa0e6bdbdeb60d14f7cc95a831fb87b63855bce04425cfbfc4c705a41632c01
Timestamp: 1713650930 Timestamp [UCT]: 2024-04-20 22:08:50 Age [y:d:h:m:s]: 00:260:02:10:04
Block: 1004910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186177 RingCT/type: yes/0
Extra: 013fa0e6bdbdeb60d14f7cc95a831fb87b63855bce04425cfbfc4c705a41632c010211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdbc1c33042791e70cfd1c595ff942a9b8a39b4396293df9c30e24c2f53b7891 0.600000000000 1465484 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": 1004920, "vin": [ { "gen": { "height": 1004910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdbc1c33042791e70cfd1c595ff942a9b8a39b4396293df9c30e24c2f53b7891" } } ], "extra": [ 1, 63, 160, 230, 189, 189, 235, 96, 209, 79, 124, 201, 90, 131, 31, 184, 123, 99, 133, 91, 206, 4, 66, 92, 251, 252, 76, 112, 90, 65, 99, 44, 1, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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