Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a01e63aae994929455a01d0bb71f797c39e8ad3ecf8eba7978bcdd2f8b73b14

Tx prefix hash: a5f3cc0979a2bc1398622aced7a9b054380fdaa2701039715e684ce9e2ff7d8f
Tx public key: 8d87e71179874a67b307b17a2ef4fc66f73749f897857e995d57d7aac5f6ae62
Timestamp: 1717130487 Timestamp [UCT]: 2024-05-31 04:41:27 Age [y:d:h:m:s]: 00:289:18:55:32
Block: 1033767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207116 RingCT/type: yes/0
Extra: 018d87e71179874a67b307b17a2ef4fc66f73749f897857e995d57d7aac5f6ae6202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55dadf87cb0ccec220bc783989e52705e793fd8554d7ed67353d00b473857ab7 0.600000000000 1502240 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": 1033777, "vin": [ { "gen": { "height": 1033767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55dadf87cb0ccec220bc783989e52705e793fd8554d7ed67353d00b473857ab7" } } ], "extra": [ 1, 141, 135, 231, 17, 121, 135, 74, 103, 179, 7, 177, 122, 46, 244, 252, 102, 247, 55, 73, 248, 151, 133, 126, 153, 93, 87, 215, 170, 197, 246, 174, 98, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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