Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94521157c27c6bdd4c7fdda0f767368f76446a5f519875e74015f0bc19311744

Tx prefix hash: f16d89b1045ab2febfc98eaa72149a7af1ff0c631d0bead65349d75e2ee0b20d
Tx public key: d49add4450f41f489255f16784b9f4520f8c1a6be8345b72d46bda302e100853
Timestamp: 1761979828 Timestamp [UCT]: 2025-11-01 06:50:28 Age [y:d:h:m:s]: 00:004:18:59:35
Block: 1402494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3387 RingCT/type: yes/0
Extra: 01d49add4450f41f489255f16784b9f4520f8c1a6be8345b72d46bda302e10085302110000000a5dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 619d552d2e0363d8f1a3aa4e4fc024968a18423d7d9abf51f970ead9858ac9d2 0.600000000000 1890813 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": 1402504, "vin": [ { "gen": { "height": 1402494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "619d552d2e0363d8f1a3aa4e4fc024968a18423d7d9abf51f970ead9858ac9d2" } } ], "extra": [ 1, 212, 154, 221, 68, 80, 244, 31, 72, 146, 85, 241, 103, 132, 185, 244, 82, 15, 140, 26, 107, 232, 52, 91, 114, 212, 107, 218, 48, 46, 16, 8, 83, 2, 17, 0, 0, 0, 10, 93, 251, 190, 42, 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