Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 290998334a03a72046ee1ae3c2e96ed9fd2c1ed3b96cb3834cf16f78b4487af1

Tx prefix hash: 9f8985d0ad1ed09dc12bf48f100184a7535e5577b18c73afe88bd41a2f1f898f
Tx public key: aca007de2778dcfbb6e3c0fac094887ea5bbfd29b937892b10763b0567679f7e
Timestamp: 1684869989 Timestamp [UCT]: 2023-05-23 19:26:29 Age [y:d:h:m:s]: 02:139:16:57:59
Block: 766569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619589 RingCT/type: yes/0
Extra: 01aca007de2778dcfbb6e3c0fac094887ea5bbfd29b937892b10763b0567679f7e021100000003faf35c9c000000000000000000

1 output(s) for total of 1.770267368000 dcy

stealth address amount amount idx
00: 8dee96eb03e93b4dab0fc5d94e06342c5fd4d282b98d139c5a99646c6d2b4245 1.770267368000 1215618 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": 766579, "vin": [ { "gen": { "height": 766569 } } ], "vout": [ { "amount": 1770267368, "target": { "key": "8dee96eb03e93b4dab0fc5d94e06342c5fd4d282b98d139c5a99646c6d2b4245" } } ], "extra": [ 1, 172, 160, 7, 222, 39, 120, 220, 251, 182, 227, 192, 250, 192, 148, 136, 126, 165, 187, 253, 41, 185, 55, 137, 43, 16, 118, 59, 5, 103, 103, 159, 126, 2, 17, 0, 0, 0, 3, 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