Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1e678182d532cd962a6edc91107d8e683eec6f732c221fb2197c588fffbd68c

Tx prefix hash: 8c0bec3ba0bd8f1031db4e90fb916ac0d1c0aac7e980927dff862dbce243b69c
Tx public key: ab49839ca259a399224b4230f89dd16d7c0ecd0f71c0743907dc0d56dccfa733
Timestamp: 1741089684 Timestamp [UCT]: 2025-03-04 12:01:24 Age [y:d:h:m:s]: 00:262:04:54:51
Block: 1231940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185139 RingCT/type: yes/0
Extra: 01ab49839ca259a399224b4230f89dd16d7c0ecd0f71c0743907dc0d56dccfa73302110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1eb3b567b8d14e1edc7cf110ffcc2441c09d7a2de33a08d4693b462ea885e4e 0.600000000000 1718851 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": 1231950, "vin": [ { "gen": { "height": 1231940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1eb3b567b8d14e1edc7cf110ffcc2441c09d7a2de33a08d4693b462ea885e4e" } } ], "extra": [ 1, 171, 73, 131, 156, 162, 89, 163, 153, 34, 75, 66, 48, 248, 157, 209, 109, 124, 14, 205, 15, 113, 192, 116, 57, 7, 220, 13, 86, 220, 207, 167, 51, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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