Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f10b2540e6a320f4010a0ec8fe1fc85007963e3e53a675ec3343b318022d3e3

Tx prefix hash: f2320c4235313758d45b4ab5b4afcd4409ca1db18970b7669a1afaa32d24e359
Tx public key: a75147d8af50462788c51b93c7d2f6eb101f8fc1ab2bcd629fa6800532a5ca73
Timestamp: 1696138904 Timestamp [UCT]: 2023-10-01 05:41:44 Age [y:d:h:m:s]: 01:183:17:53:55
Block: 859938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392363 RingCT/type: yes/0
Extra: 01a75147d8af50462788c51b93c7d2f6eb101f8fc1ab2bcd629fa6800532a5ca7302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.868337340000 dcy

stealth address amount amount idx
00: 917de061ddc6d0d95e0112653e8418c1dc8f4fd70ceaf60e358fc869f17377a3 0.868337340000 1314192 of 0

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": 859948, "vin": [ { "gen": { "height": 859938 } } ], "vout": [ { "amount": 868337340, "target": { "key": "917de061ddc6d0d95e0112653e8418c1dc8f4fd70ceaf60e358fc869f17377a3" } } ], "extra": [ 1, 167, 81, 71, 216, 175, 80, 70, 39, 136, 197, 27, 147, 199, 210, 246, 235, 16, 31, 143, 193, 171, 43, 205, 98, 159, 166, 128, 5, 50, 165, 202, 115, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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