Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cc86a932449f0441b051d3d925e16b2e0ea459077e230db73a97959edec08cf

Tx prefix hash: 8dd69a9e0ebcd8170abde152531cafd23f852900a5acea69076906df147ab292
Tx public key: 9d177a03654831c45f80aaf7dfde9a3c6453c1a755e1e26d8d337c7df9fa793d
Timestamp: 1659621246 Timestamp [UCT]: 2022-08-04 13:54:06 Age [y:d:h:m:s]: 02:257:17:36:13
Block: 558574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705422 RingCT/type: yes/0
Extra: 019d177a03654831c45f80aaf7dfde9a3c6453c1a755e1e26d8d337c7df9fa793d021100000004e6d27f9c000000000000000000

1 output(s) for total of 8.653914152000 dcy

stealth address amount amount idx
00: 7ee429f40fd9c8a9f0f6ebb1f38a06604c493144285958872804bbdbe07b2e97 8.653914152000 990660 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": 558584, "vin": [ { "gen": { "height": 558574 } } ], "vout": [ { "amount": 8653914152, "target": { "key": "7ee429f40fd9c8a9f0f6ebb1f38a06604c493144285958872804bbdbe07b2e97" } } ], "extra": [ 1, 157, 23, 122, 3, 101, 72, 49, 196, 95, 128, 170, 247, 223, 222, 154, 60, 100, 83, 193, 167, 85, 225, 226, 109, 141, 51, 124, 125, 249, 250, 121, 61, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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