Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7071cb62acfe3d55a751e2341ab026a406818ed1f20ec5ddb0bd556f2d8c34

Tx prefix hash: 8176f65db647a4355681b1a40d79bc0aed2c75a896496e9cec81b21526a861c5
Tx public key: 95e0e17d8e50d89dcacb737fc65427116de6d3873798a75e63a8ad7aee470937
Timestamp: 1741350716 Timestamp [UCT]: 2025-03-07 12:31:56 Age [y:d:h:m:s]: 00:259:03:23:42
Block: 1234106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182937 RingCT/type: yes/0
Extra: 0195e0e17d8e50d89dcacb737fc65427116de6d3873798a75e63a8ad7aee47093702110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7f896074d45e29d14e0be11ac016fef4fe0ac487092fea8ea87017db4d00c20 0.600000000000 1721031 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": 1234116, "vin": [ { "gen": { "height": 1234106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7f896074d45e29d14e0be11ac016fef4fe0ac487092fea8ea87017db4d00c20" } } ], "extra": [ 1, 149, 224, 225, 125, 142, 80, 216, 157, 202, 203, 115, 127, 198, 84, 39, 17, 109, 230, 211, 135, 55, 152, 167, 94, 99, 168, 173, 122, 238, 71, 9, 55, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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