Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49a9da4e8469c81ecdbf4903a7afec2cb21c9c26229175496bde6d586ef4e00

Tx prefix hash: 3d80648332f28b085b15dbc07268a47b407cb366d7ab9cf1bcafaa0aee1a58a6
Tx public key: e75e42d1ac1d123400cbb7e43709436f614ba07fb366870c8b4ec9cf7f685a83
Timestamp: 1766293003 Timestamp [UCT]: 2025-12-21 04:56:43 Age [y:d:h:m:s]: 00:001:05:48:41
Block: 1438217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 880 RingCT/type: yes/0
Extra: 01e75e42d1ac1d123400cbb7e43709436f614ba07fb366870c8b4ec9cf7f685a8302110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a0d38a929bea3c3ed5aae38d9e07393d9121307b3ebee143d2ab3a24d0aeae 0.600000000000 1927034 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": 1438227, "vin": [ { "gen": { "height": 1438217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a0d38a929bea3c3ed5aae38d9e07393d9121307b3ebee143d2ab3a24d0aeae" } } ], "extra": [ 1, 231, 94, 66, 209, 172, 29, 18, 52, 0, 203, 183, 228, 55, 9, 67, 111, 97, 75, 160, 127, 179, 102, 135, 12, 139, 78, 201, 207, 127, 104, 90, 131, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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