Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a11f58c8c7edff1feedcbe36d56c4b09d3053fa1d65d916463e3ee275504b33d

Tx prefix hash: cffac911915a03e73acec3bcfd6b08ea921e01d35b76a17641f85079d20c7c6d
Tx public key: 4bda7eaa9d59a39697fafa5623068c92b22dd1f8b30a28c128f1691d9ff145dd
Timestamp: 1717644159 Timestamp [UCT]: 2024-06-06 03:22:39 Age [y:d:h:m:s]: 00:214:05:40:12
Block: 1038024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153335 RingCT/type: yes/0
Extra: 014bda7eaa9d59a39697fafa5623068c92b22dd1f8b30a28c128f1691d9ff145dd02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 768f76cf73d7967846964b22df9a13dacfe3ec4f05f70ab1669310d23e1117fd 0.600000000000 1506583 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": 1038034, "vin": [ { "gen": { "height": 1038024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "768f76cf73d7967846964b22df9a13dacfe3ec4f05f70ab1669310d23e1117fd" } } ], "extra": [ 1, 75, 218, 126, 170, 157, 89, 163, 150, 151, 250, 250, 86, 35, 6, 140, 146, 178, 45, 209, 248, 179, 10, 40, 193, 40, 241, 105, 29, 159, 241, 69, 221, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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