Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0f316f247d46efa33a3801ba2ff81f5d7e8bd9d114969321316c508387daff0

Tx prefix hash: 87c56244b8eaf9fc394012fee5054ae92470f5073e65e130af2ed9b7c0329b8b
Tx public key: 7870e191f597f7dc6dcf03f4fbe754a790f9c771e2c7be46fac759dcaeee52dc
Timestamp: 1751882879 Timestamp [UCT]: 2025-07-07 10:07:59 Age [y:d:h:m:s]: 00:128:01:02:47
Block: 1320548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89925 RingCT/type: yes/0
Extra: 017870e191f597f7dc6dcf03f4fbe754a790f9c771e2c7be46fac759dcaeee52dc02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dfcb6eddde54a575aec4cd2837edeeb15ad0c09e89c52211fb2789ce8c1bf6e 0.600000000000 1808247 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": 1320558, "vin": [ { "gen": { "height": 1320548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dfcb6eddde54a575aec4cd2837edeeb15ad0c09e89c52211fb2789ce8c1bf6e" } } ], "extra": [ 1, 120, 112, 225, 145, 245, 151, 247, 220, 109, 207, 3, 244, 251, 231, 84, 167, 144, 249, 199, 113, 226, 199, 190, 70, 250, 199, 89, 220, 174, 238, 82, 220, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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