Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49fc7ceca74f95c7cfb8033b1762ac0d4a4b0e0eced9aa61cc4349264e492e3c

Tx prefix hash: 507c7b3cf016d1f1e92530a015a8fd77553ed3b6a31e3a9a5a451ada9f644e23
Tx public key: bce3ca091a32b9715769bb88213f2c17fd3e269e018c5fe9aee17033c4dc50f9
Timestamp: 1648866579 Timestamp [UCT]: 2022-04-02 02:29:39 Age [y:d:h:m:s]: 02:311:16:08:39
Block: 471329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742217 RingCT/type: yes/0
Extra: 01bce3ca091a32b9715769bb88213f2c17fd3e269e018c5fe9aee17033c4dc50f9021100000006d3fcec30000000000000000000

1 output(s) for total of 16.838042933000 dcy

stealth address amount amount idx
00: 63b357eeca9a08dcdd0fa45022e0cc74f613ec3573f7bfd07f4a735567346644 16.838042933000 890649 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": 471339, "vin": [ { "gen": { "height": 471329 } } ], "vout": [ { "amount": 16838042933, "target": { "key": "63b357eeca9a08dcdd0fa45022e0cc74f613ec3573f7bfd07f4a735567346644" } } ], "extra": [ 1, 188, 227, 202, 9, 26, 50, 185, 113, 87, 105, 187, 136, 33, 63, 44, 23, 253, 62, 38, 158, 1, 140, 95, 233, 174, 225, 112, 51, 196, 220, 80, 249, 2, 17, 0, 0, 0, 6, 211, 252, 236, 48, 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