Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e31d20c314d8ce1fe2fff093caeaeddad0cf085447424d13767e22bd23035d10

Tx prefix hash: 95509988e65263b93621e8facab9bb909f0a7ca46d8f180c68047f9d0d6210e0
Tx public key: 1e883b39b1cd23fb96b2abdb8d1f1bfa428d7981a9edf956dfc1d7891c152460
Timestamp: 1721719096 Timestamp [UCT]: 2024-07-23 07:18:16 Age [y:d:h:m:s]: 00:216:13:42:35
Block: 1071802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154668 RingCT/type: yes/0
Extra: 011e883b39b1cd23fb96b2abdb8d1f1bfa428d7981a9edf956dfc1d7891c152460021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a801753aa7e7b35f831e18f249b1390bd031b14f0c4b05b5b06cacb4e7f8cb3 0.600000000000 1544165 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": 1071812, "vin": [ { "gen": { "height": 1071802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a801753aa7e7b35f831e18f249b1390bd031b14f0c4b05b5b06cacb4e7f8cb3" } } ], "extra": [ 1, 30, 136, 59, 57, 177, 205, 35, 251, 150, 178, 171, 219, 141, 31, 27, 250, 66, 141, 121, 129, 169, 237, 249, 86, 223, 193, 215, 137, 28, 21, 36, 96, 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