Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 362c0238920fbc2a93d610e537b07395589f13136a4974c4642645993c179f19

Tx prefix hash: b8363eaea5cfbb67175a469a0baa26d629e234c89e3623b6e0540c7a60494344
Tx public key: d0ec31340e6b102452f33e8bb2f359a73e41c341ed34b1bd0fdb84e57c00781c
Timestamp: 1588735273 Timestamp [UCT]: 2020-05-06 03:21:13 Age [y:d:h:m:s]: 04:308:01:45:49
Block: 98818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136506 RingCT/type: yes/0
Extra: 01d0ec31340e6b102452f33e8bb2f359a73e41c341ed34b1bd0fdb84e57c00781c0211000000f737fb5df4000000000000000000

1 output(s) for total of 288.785716068000 dcy

stealth address amount amount idx
00: 0b4f3aa7fabd71d405f345c3243f8268ba59e3791102d626152d303bd25c044c 288.785716068000 174588 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": 98828, "vin": [ { "gen": { "height": 98818 } } ], "vout": [ { "amount": 288785716068, "target": { "key": "0b4f3aa7fabd71d405f345c3243f8268ba59e3791102d626152d303bd25c044c" } } ], "extra": [ 1, 208, 236, 49, 52, 14, 107, 16, 36, 82, 243, 62, 139, 178, 243, 89, 167, 62, 65, 195, 65, 237, 52, 177, 189, 15, 219, 132, 229, 124, 0, 120, 28, 2, 17, 0, 0, 0, 247, 55, 251, 93, 244, 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