Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15bfc4242397c1686d80afec93ad6635873f392715e0c2a8a3a501ef30a70612

Tx prefix hash: 0770441e3dafcb034fd3ad846cd7c89591681b5261efd97140fd1c4a768edfe6
Tx public key: 4f6eefec49f9caad74c537a7e22ff712010a4627718d3c504a9cc061df38bf4f
Timestamp: 1755392560 Timestamp [UCT]: 2025-08-17 01:02:40 Age [y:d:h:m:s]: 00:095:17:52:57
Block: 1348174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68253 RingCT/type: yes/0
Extra: 014f6eefec49f9caad74c537a7e22ff712010a4627718d3c504a9cc061df38bf4f021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2b4df94ac31b03e202719fd0d5acf41a71b08f606dfa5c1deb2a8d3ae8a91b9 0.600000000000 1836097 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": 1348184, "vin": [ { "gen": { "height": 1348174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2b4df94ac31b03e202719fd0d5acf41a71b08f606dfa5c1deb2a8d3ae8a91b9" } } ], "extra": [ 1, 79, 110, 239, 236, 73, 249, 202, 173, 116, 197, 55, 167, 226, 47, 247, 18, 1, 10, 70, 39, 113, 141, 60, 80, 74, 156, 192, 97, 223, 56, 191, 79, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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