Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826057cad913655bed3fe9acb1353a53d45f9efb220d1eaa7850dc48cf7ac765

Tx prefix hash: 006cdd550b9ef470ec9c27ce55ce9e63ffa1a2780a0839baf9cb243a38fd56b3
Tx public key: d826ebdb57ce4d2f0eb4a9c3c14d2693421c55d77b6cb022e088d71fdb1dde1a
Timestamp: 1731567722 Timestamp [UCT]: 2024-11-14 07:02:02 Age [y:d:h:m:s]: 00:328:16:09:58
Block: 1153372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232387 RingCT/type: yes/0
Extra: 01d826ebdb57ce4d2f0eb4a9c3c14d2693421c55d77b6cb022e088d71fdb1dde1a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22c70da7caff23a7c7261568055f6c63bda6e4a4a4d0747fcc1b0ea5fed496f4 0.600000000000 1638981 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": 1153382, "vin": [ { "gen": { "height": 1153372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22c70da7caff23a7c7261568055f6c63bda6e4a4a4d0747fcc1b0ea5fed496f4" } } ], "extra": [ 1, 216, 38, 235, 219, 87, 206, 77, 47, 14, 180, 169, 195, 193, 77, 38, 147, 66, 28, 85, 215, 123, 108, 176, 34, 224, 136, 215, 31, 219, 29, 222, 26, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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