Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1b266d0e9381838b6ca2c295a990840d55c6f1d8d6d8025bff4808e831651b

Tx prefix hash: 552e4ee59da2294287b43d74399bf0b668dece12debbbde1bdc91ef2fe107b61
Tx public key: f72d5243bd05fd8cb024a2068bc8b606d2fcaa5fef07b29447f27dd046cd4117
Timestamp: 1724971864 Timestamp [UCT]: 2024-08-29 22:51:04 Age [y:d:h:m:s]: 00:267:12:48:37
Block: 1098766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191104 RingCT/type: yes/0
Extra: 01f72d5243bd05fd8cb024a2068bc8b606d2fcaa5fef07b29447f27dd046cd411702110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16d36845d975de07a57fafc827bf4c87ff7d34a46eee4e7bad8ca0b359f81e71 0.600000000000 1574597 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": 1098776, "vin": [ { "gen": { "height": 1098766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d36845d975de07a57fafc827bf4c87ff7d34a46eee4e7bad8ca0b359f81e71" } } ], "extra": [ 1, 247, 45, 82, 67, 189, 5, 253, 140, 176, 36, 162, 6, 139, 200, 182, 6, 210, 252, 170, 95, 239, 7, 178, 148, 71, 242, 125, 208, 70, 205, 65, 23, 2, 17, 0, 0, 0, 18, 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