Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9d42239e6336c98bcf57d71850cb6bc518edbea9dcb1ba48a39371859bc78e

Tx prefix hash: 542ebc39f4faebfc823a140d38b55d3ce58261cb20d0602084bee8d9a630eae0
Tx public key: 18dda7d86e1c800cffd2f2ac29a588c3bc21df30f3ec131caca586e83711b5c3
Timestamp: 1677425748 Timestamp [UCT]: 2023-02-26 15:35:48 Age [y:d:h:m:s]: 02:032:15:31:23
Block: 705475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544909 RingCT/type: yes/0
Extra: 0118dda7d86e1c800cffd2f2ac29a588c3bc21df30f3ec131caca586e83711b5c3021100000002835e4d22000000000000000000

1 output(s) for total of 2.821424113000 dcy

stealth address amount amount idx
00: 3c2847d0c510d1e26f0840d8c9240a9c8e8a3c1d24a743e1bf23725c0b1f3d64 2.821424113000 1149176 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": 705485, "vin": [ { "gen": { "height": 705475 } } ], "vout": [ { "amount": 2821424113, "target": { "key": "3c2847d0c510d1e26f0840d8c9240a9c8e8a3c1d24a743e1bf23725c0b1f3d64" } } ], "extra": [ 1, 24, 221, 167, 216, 110, 28, 128, 12, 255, 210, 242, 172, 41, 165, 136, 195, 188, 33, 223, 48, 243, 236, 19, 28, 172, 165, 134, 232, 55, 17, 181, 195, 2, 17, 0, 0, 0, 2, 131, 94, 77, 34, 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