Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f662180bff40eb4ff7e4d414723aced30c1b1bcfc0c7e31e34ed221c3387e1e

Tx prefix hash: bde20b7ffe171f2610f04286f53dfb770e9c627a99c2e70d454711ed065f096e
Tx public key: 6b33387e776503075db75e9420e2a1c237bf08aa63e2642e2e08a324d76724a1
Timestamp: 1761017921 Timestamp [UCT]: 2025-10-21 03:38:41 Age [y:d:h:m:s]: 00:081:16:19:18
Block: 1394512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58479 RingCT/type: yes/0
Extra: 016b33387e776503075db75e9420e2a1c237bf08aa63e2642e2e08a324d76724a102110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a67eede2e68d4f17381badd8e682399ea91c0e4b548d17b5eb2dd09c0b2bc688 0.600000000000 1882783 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": 1394522, "vin": [ { "gen": { "height": 1394512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a67eede2e68d4f17381badd8e682399ea91c0e4b548d17b5eb2dd09c0b2bc688" } } ], "extra": [ 1, 107, 51, 56, 126, 119, 101, 3, 7, 93, 183, 94, 148, 32, 226, 161, 194, 55, 191, 8, 170, 99, 226, 100, 46, 46, 8, 163, 36, 215, 103, 36, 161, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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