Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b00ef9a4dcfd4cdfb541a160c60f64158fa097a4b40b08f108cc11c13244a3

Tx prefix hash: 2fb2f4f69c8f2f315c8fd22c6424656853ee7f6145cbeeb2c5ab127cb30e59c7
Tx public key: 0f8e2327b5ab9ca11d2d78948caf35deb229f8309ddb5b81b745046967dd077a
Timestamp: 1756077683 Timestamp [UCT]: 2025-08-24 23:21:23 Age [y:d:h:m:s]: 00:093:15:11:19
Block: 1353736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66858 RingCT/type: yes/0
Extra: 010f8e2327b5ab9ca11d2d78948caf35deb229f8309ddb5b81b745046967dd077a0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fbdf40634d17651f9d23a73c3fb99dd8a7728c585bd2dadccefdf88266373a0 0.600000000000 1841713 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": 1353746, "vin": [ { "gen": { "height": 1353736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fbdf40634d17651f9d23a73c3fb99dd8a7728c585bd2dadccefdf88266373a0" } } ], "extra": [ 1, 15, 142, 35, 39, 181, 171, 156, 161, 29, 45, 120, 148, 140, 175, 53, 222, 178, 41, 248, 48, 157, 219, 91, 129, 183, 69, 4, 105, 103, 221, 7, 122, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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