Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c90d6bf1f24fa0d1f6c7150b71c7c59f610db3f3445f16e2311d77f4219237

Tx prefix hash: 046c23a5958af79c57d98a11645043d6a084974d08a79d1563802dcac16f5676
Tx public key: 8cfdeb7e7ac6b437f581f3dfcfd03cc968a2dd4f509d8925bd40a3842e1bbd52
Timestamp: 1749848260 Timestamp [UCT]: 2025-06-13 20:57:40 Age [y:d:h:m:s]: 00:160:12:33:37
Block: 1304366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112488 RingCT/type: yes/0
Extra: 018cfdeb7e7ac6b437f581f3dfcfd03cc968a2dd4f509d8925bd40a3842e1bbd52021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 362cf1531594d4c46fe0f0da5340dad0c236a8e42548662b84ce0ded9abe8a10 0.600000000000 1791955 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": 1304376, "vin": [ { "gen": { "height": 1304366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "362cf1531594d4c46fe0f0da5340dad0c236a8e42548662b84ce0ded9abe8a10" } } ], "extra": [ 1, 140, 253, 235, 126, 122, 198, 180, 55, 245, 129, 243, 223, 207, 208, 60, 201, 104, 162, 221, 79, 80, 157, 137, 37, 189, 64, 163, 132, 46, 27, 189, 82, 2, 17, 0, 0, 0, 2, 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