Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0171df36e0637187e2785bd9efda5d1fe34c6d72b8d5f171aec3094d3eb9d3

Tx prefix hash: f4914cacb8c70cdc76a0d39c050b382fe0a422bbb17cc09445e42afb44f399e4
Tx public key: e5dee64e0adc6b3e1464b875b6fce09e0bea0e17149951d7dd8f494cdad851b8
Timestamp: 1744721267 Timestamp [UCT]: 2025-04-15 12:47:47 Age [y:d:h:m:s]: 00:259:16:26:56
Block: 1261996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183381 RingCT/type: yes/0
Extra: 01e5dee64e0adc6b3e1464b875b6fce09e0bea0e17149951d7dd8f494cdad851b8021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb47d2ecb3337eade4fef7e6b2e91ecd34e005be90a56c84d3600c1894b592a2 0.600000000000 1749173 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": 1262006, "vin": [ { "gen": { "height": 1261996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb47d2ecb3337eade4fef7e6b2e91ecd34e005be90a56c84d3600c1894b592a2" } } ], "extra": [ 1, 229, 222, 230, 78, 10, 220, 107, 62, 20, 100, 184, 117, 182, 252, 224, 158, 11, 234, 14, 23, 20, 153, 81, 215, 221, 143, 73, 76, 218, 216, 81, 184, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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