Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60b7c8dc6233c95134ee9e0753eaf5490a799ac10742b2cf960baf5878d6fd4

Tx prefix hash: 5a56b38ffeb8d74393ff49dd9ec34edec5b1c3b81563927bbc7774e8677e946c
Tx public key: a11fc63ebc8c9f2ac9be4fa8d84093beb7293b74eee3536d5934d20bcf7e02f7
Timestamp: 1751015243 Timestamp [UCT]: 2025-06-27 09:07:23 Age [y:d:h:m:s]: 00:141:17:20:47
Block: 1313769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99310 RingCT/type: yes/0
Extra: 01a11fc63ebc8c9f2ac9be4fa8d84093beb7293b74eee3536d5934d20bcf7e02f7021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b290ba6664b7bc574e71b4fdecf77541009c4a795f0a0ec8a484579a8b8cce3 0.600000000000 1801412 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": 1313779, "vin": [ { "gen": { "height": 1313769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b290ba6664b7bc574e71b4fdecf77541009c4a795f0a0ec8a484579a8b8cce3" } } ], "extra": [ 1, 161, 31, 198, 62, 188, 140, 159, 42, 201, 190, 79, 168, 216, 64, 147, 190, 183, 41, 59, 116, 238, 227, 83, 109, 89, 52, 210, 11, 207, 126, 2, 247, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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