Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d971d7b38516839aa8101f038ca3a9363fd09d259218be07522b17b0882cff4

Tx prefix hash: 2aacb2665cdd3f20f867b2b09f7ae0b6fff17c973b855d863d510fd8b85089d5
Tx public key: 45bcbc519e4afaffee1ad18f0b3d39a53b41d9a107d0780557982cd0894ae9a0
Timestamp: 1714690818 Timestamp [UCT]: 2024-05-02 23:00:18 Age [y:d:h:m:s]: 00:357:20:52:08
Block: 1013549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255822 RingCT/type: yes/0
Extra: 0145bcbc519e4afaffee1ad18f0b3d39a53b41d9a107d0780557982cd0894ae9a002110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ef4bb277f382cc4d419a70d954e94b1ec0f690b37d0a61d611cfff47feecc57 0.600000000000 1476396 of 15

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": 1013559, "vin": [ { "gen": { "height": 1013549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ef4bb277f382cc4d419a70d954e94b1ec0f690b37d0a61d611cfff47feecc57" } } ], "extra": [ 1, 69, 188, 188, 81, 158, 74, 250, 255, 238, 26, 209, 143, 11, 61, 57, 165, 59, 65, 217, 161, 7, 208, 120, 5, 87, 152, 44, 208, 137, 74, 233, 160, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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