Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e67f2f728058063ee16972a9eb011f62ea19ceec92a5c3721a64d7663d6c546

Tx prefix hash: 6f0effec49ccfd5bb85621a2537deb0605f94af538899b09108474de3f93d5a0
Tx public key: 891c0fa5f10f554d252dbdfd7cef553403b19913a0fc3f9f3ba6eb602e6fb4ef
Timestamp: 1726237985 Timestamp [UCT]: 2024-09-13 14:33:05 Age [y:d:h:m:s]: 01:053:08:10:15
Block: 1109266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296531 RingCT/type: yes/0
Extra: 01891c0fa5f10f554d252dbdfd7cef553403b19913a0fc3f9f3ba6eb602e6fb4ef021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cd6144d01dce9965b36513c88e7d03b3f58bbae95c07a060ffa94b885741643 0.600000000000 1587457 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": 1109276, "vin": [ { "gen": { "height": 1109266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd6144d01dce9965b36513c88e7d03b3f58bbae95c07a060ffa94b885741643" } } ], "extra": [ 1, 137, 28, 15, 165, 241, 15, 85, 77, 37, 45, 189, 253, 124, 239, 85, 52, 3, 177, 153, 19, 160, 252, 63, 159, 59, 166, 235, 96, 46, 111, 180, 239, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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