Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 518e1c76db56e46d27cf5d6cf339b8a0fa14505af468273dbfd067f04774316b

Tx prefix hash: e981b29c51eb6cb5d967412b8e3963c429abe9a4f7a01a0aa2dca719a3d3502b
Tx public key: e7b87ee04ee8cb19892a4c467fea08787b911a660fdf81e3b8c91e32f60aa9b3
Timestamp: 1765086449 Timestamp [UCT]: 2025-12-07 05:47:29 Age [y:d:h:m:s]: 00:014:20:28:57
Block: 1428208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10641 RingCT/type: yes/0
Extra: 01e7b87ee04ee8cb19892a4c467fea08787b911a660fdf81e3b8c91e32f60aa9b3021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f33e5ea4b6b1ff6176063889c6d25b5d807218149128523e1794b47ac3f91de 0.600000000000 1916921 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": 1428218, "vin": [ { "gen": { "height": 1428208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f33e5ea4b6b1ff6176063889c6d25b5d807218149128523e1794b47ac3f91de" } } ], "extra": [ 1, 231, 184, 126, 224, 78, 232, 203, 25, 137, 42, 76, 70, 127, 234, 8, 120, 123, 145, 26, 102, 15, 223, 129, 227, 184, 201, 30, 50, 246, 10, 169, 179, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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