Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8538891f276c2f084e79aea9489b50cb1761ac28b88927e3281e07d5667efd4

Tx prefix hash: 03636c1063ee3386a5a609fee597851964e8667b2187a49908e2093564aa527e
Tx public key: e6894f5b31eb795d9e722f2a7aac7a0a9601ef09f939ac16cd5ae94987ad9d7b
Timestamp: 1697646707 Timestamp [UCT]: 2023-10-18 16:31:47 Age [y:d:h:m:s]: 01:243:03:34:43
Block: 872439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434736 RingCT/type: yes/0
Extra: 01e6894f5b31eb795d9e722f2a7aac7a0a9601ef09f939ac16cd5ae94987ad9d7b021100000002faf35c9c000000000000000000

1 output(s) for total of 0.789309718000 dcy

stealth address amount amount idx
00: 1a3a4cb32ae65e353d4c36ae5b9bd4e65cd5fc32a7fbb8872a31e11f28eeeab3 0.789309718000 1327527 of 0

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": 872449, "vin": [ { "gen": { "height": 872439 } } ], "vout": [ { "amount": 789309718, "target": { "key": "1a3a4cb32ae65e353d4c36ae5b9bd4e65cd5fc32a7fbb8872a31e11f28eeeab3" } } ], "extra": [ 1, 230, 137, 79, 91, 49, 235, 121, 93, 158, 114, 47, 42, 122, 172, 122, 10, 150, 1, 239, 9, 249, 57, 172, 22, 205, 90, 233, 73, 135, 173, 157, 123, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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