Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffe2b8046f08c5c68af54ab3c639b3682675b86b5aa47e34183d32e9f92ff91

Tx prefix hash: 1a41a306f102d675a2669f225b71dfdb94d953301a4d5ee4e478ad8421b40e9f
Tx public key: 2b264bfcdd4b5de8edee3f4795d900182e48377bc0cc9ab324e38b658242ef1e
Timestamp: 1762110768 Timestamp [UCT]: 2025-11-02 19:12:48 Age [y:d:h:m:s]: 00:090:00:17:33
Block: 1403538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64281 RingCT/type: yes/0
Extra: 012b264bfcdd4b5de8edee3f4795d900182e48377bc0cc9ab324e38b658242ef1e02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b15bdf544b7bfee517258c33f87ab1b68b33727b70fa2e36715a3e6d6c6be2f 0.600000000000 1891885 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": 1403548, "vin": [ { "gen": { "height": 1403538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b15bdf544b7bfee517258c33f87ab1b68b33727b70fa2e36715a3e6d6c6be2f" } } ], "extra": [ 1, 43, 38, 75, 252, 221, 75, 93, 232, 237, 238, 63, 71, 149, 217, 0, 24, 46, 72, 55, 123, 192, 204, 154, 179, 36, 227, 139, 101, 130, 66, 239, 30, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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