Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dbad4f7c8f8f4ec8ed611b76cd9e0df4a624d130d0c14768539afac67165705

Tx prefix hash: 8c65e60153dd1f63f8474b41ee83bc04cfb085240e2d6172704f8de66b6041f5
Tx public key: 9cb0d2d76281a20542da2b09970f588959ce30081e963330508060f6c4c22ded
Timestamp: 1659141349 Timestamp [UCT]: 2022-07-30 00:35:49 Age [y:d:h:m:s]: 02:271:02:22:28
Block: 554622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714952 RingCT/type: yes/0
Extra: 019cb0d2d76281a20542da2b09970f588959ce30081e963330508060f6c4c22ded021100000001aac913b7000000000000000000

1 output(s) for total of 8.918816014000 dcy

stealth address amount amount idx
00: a5f7f0f1846222d9889b0faf241d1d4afb36555ff63f2f9decbe624a0cc12ad9 8.918816014000 986478 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": 554632, "vin": [ { "gen": { "height": 554622 } } ], "vout": [ { "amount": 8918816014, "target": { "key": "a5f7f0f1846222d9889b0faf241d1d4afb36555ff63f2f9decbe624a0cc12ad9" } } ], "extra": [ 1, 156, 176, 210, 215, 98, 129, 162, 5, 66, 218, 43, 9, 151, 15, 88, 137, 89, 206, 48, 8, 30, 150, 51, 48, 80, 128, 96, 246, 196, 194, 45, 237, 2, 17, 0, 0, 0, 1, 170, 201, 19, 183, 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