Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf4c6bb6234351c26ac384ce2a33b02afc470cfb7a6d4254458522af0b15ab07

Tx prefix hash: ee7e463524f3294fd94e801b49e98f059b52d97123da6c5e50afd72b659ad603
Tx public key: e464415a58f295a8b5fde65a32c7673c86b1c659fb32176f5c40d378bce8082a
Timestamp: 1706602163 Timestamp [UCT]: 2024-01-30 08:09:23 Age [y:d:h:m:s]: 01:061:22:34:26
Block: 946463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305340 RingCT/type: yes/0
Extra: 01e464415a58f295a8b5fde65a32c7673c86b1c659fb32176f5c40d378bce8082a02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffae84dbc57551085e37adfe2d7dd5626ed29c258683000b29707a8a6e094f59 0.600000000000 1404795 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": 946473, "vin": [ { "gen": { "height": 946463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffae84dbc57551085e37adfe2d7dd5626ed29c258683000b29707a8a6e094f59" } } ], "extra": [ 1, 228, 100, 65, 90, 88, 242, 149, 168, 181, 253, 230, 90, 50, 199, 103, 60, 134, 177, 198, 89, 251, 50, 23, 111, 92, 64, 211, 120, 188, 232, 8, 42, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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