Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4146db5d0b7e98c5a394304ba6bee579282825d0aed410f14946c7274af3cbf3

Tx prefix hash: 1cf60af0e99671c65c4f4edd356e56c68c4d319448ef24784d0900e50e6dc75a
Tx public key: add895cc75d8d4b6c2834d451c817cfc9f97f9b7ce561200e83dcd775041e637
Timestamp: 1726228634 Timestamp [UCT]: 2024-09-13 11:57:14 Age [y:d:h:m:s]: 00:245:14:59:41
Block: 1109189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175414 RingCT/type: yes/0
Extra: 01add895cc75d8d4b6c2834d451c817cfc9f97f9b7ce561200e83dcd775041e637021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b5cd9f1a66e05eecb538c6f093245318c1c8e465e3660d8a48288fa71e67e89 0.600000000000 1587350 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": 1109199, "vin": [ { "gen": { "height": 1109189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b5cd9f1a66e05eecb538c6f093245318c1c8e465e3660d8a48288fa71e67e89" } } ], "extra": [ 1, 173, 216, 149, 204, 117, 216, 212, 182, 194, 131, 77, 69, 28, 129, 124, 252, 159, 151, 249, 183, 206, 86, 18, 0, 232, 61, 205, 119, 80, 65, 230, 55, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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