Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ccdda6081ec44771136832fcaa541d8c0f8abc4fd5d04409f3747c8336fa484

Tx prefix hash: 6407e95f7e934d65b70fdd4c3421ec4d9e5af4a5361ba250c263dcc055ea55f3
Tx public key: af717d8c374f4e81b063f428d25105dcb6863ba79e03d815abe9e78920311c69
Timestamp: 1644170164 Timestamp [UCT]: 2022-02-06 17:56:04 Age [y:d:h:m:s]: 03:082:02:12:53
Block: 433371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 838158 RingCT/type: yes/0
Extra: 01af717d8c374f4e81b063f428d25105dcb6863ba79e03d815abe9e78920311c690211000000084a0f5013000000000000000000

1 output(s) for total of 22.494161509000 dcy

stealth address amount amount idx
00: 46c4070d34a58b793d7a8bea869f5e6305a8b440bef55c1ce5ee94e12f379f0e 22.494161509000 844046 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": 433381, "vin": [ { "gen": { "height": 433371 } } ], "vout": [ { "amount": 22494161509, "target": { "key": "46c4070d34a58b793d7a8bea869f5e6305a8b440bef55c1ce5ee94e12f379f0e" } } ], "extra": [ 1, 175, 113, 125, 140, 55, 79, 78, 129, 176, 99, 244, 40, 210, 81, 5, 220, 182, 134, 59, 167, 158, 3, 216, 21, 171, 233, 231, 137, 32, 49, 28, 105, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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