Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033f1f281a892d11dafc117528f896159b857b5f039102404719aa17cff1a139

Tx prefix hash: d84f81657365bd90fd0af0caf688ff27ac4caa817092f40e8f3126f49e5bf6fc
Tx public key: 07ae1e4be90a19b2c11a1568071f39a87afea4b75f1e6e2b5507178fc17670ed
Timestamp: 1722119866 Timestamp [UCT]: 2024-07-27 22:37:46 Age [y:d:h:m:s]: 01:106:02:37:07
Block: 1075129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334326 RingCT/type: yes/0
Extra: 0107ae1e4be90a19b2c11a1568071f39a87afea4b75f1e6e2b5507178fc17670ed02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46f73a7bfad86951038522f5c8f1adc12fae3a4bc28538e3cc1867b613bbc3f3 0.600000000000 1547652 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": 1075139, "vin": [ { "gen": { "height": 1075129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46f73a7bfad86951038522f5c8f1adc12fae3a4bc28538e3cc1867b613bbc3f3" } } ], "extra": [ 1, 7, 174, 30, 75, 233, 10, 25, 178, 193, 26, 21, 104, 7, 31, 57, 168, 122, 254, 164, 183, 95, 30, 110, 43, 85, 7, 23, 143, 193, 118, 112, 237, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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