Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e7692b4ef2986eadb7dc4c69048cf77e0ac078f682dbf7f258816ccdb685082

Tx prefix hash: a56c505824ee327951d670517953748001ddc5b5e7f17ecf89fe8f7d4e43c0b1
Tx public key: 7ba3dd5a007679607806f86b17f9af5e2631c7e202bec295b5aca5632a296dc7
Timestamp: 1721829545 Timestamp [UCT]: 2024-07-24 13:59:05 Age [y:d:h:m:s]: 00:251:01:37:52
Block: 1072713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179351 RingCT/type: yes/0
Extra: 017ba3dd5a007679607806f86b17f9af5e2631c7e202bec295b5aca5632a296dc7021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79f7b617ae7948f1d3faff8b076eb48cd2fff5e5fd8b3021073a4874b72056c2 0.600000000000 1545206 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": 1072723, "vin": [ { "gen": { "height": 1072713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79f7b617ae7948f1d3faff8b076eb48cd2fff5e5fd8b3021073a4874b72056c2" } } ], "extra": [ 1, 123, 163, 221, 90, 0, 118, 121, 96, 120, 6, 248, 107, 23, 249, 175, 94, 38, 49, 199, 226, 2, 190, 194, 149, 181, 172, 165, 99, 42, 41, 109, 199, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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