Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b95c125f32d552e897e71f6692f7e597ccfb4d0f6a8983b465169acc5fcb4223

Tx prefix hash: 1d9b79ce413677d795afb1400ebf537026fdccc8512cec8593daa9ee6cac1b63
Tx public key: 2c6070c04954e65a6e1fd0b1a7e817ade74710a4e2a556e46e76cca12ede483a
Timestamp: 1705578669 Timestamp [UCT]: 2024-01-18 11:51:09 Age [y:d:h:m:s]: 01:080:18:40:39
Block: 937982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318812 RingCT/type: yes/0
Extra: 012c6070c04954e65a6e1fd0b1a7e817ade74710a4e2a556e46e76cca12ede483a02110000000e7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4401712f9f9db80d7633775cf44cd49b9e82e9dbba8d19d67bcb467828203b9c 0.600000000000 1396046 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": 937992, "vin": [ { "gen": { "height": 937982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4401712f9f9db80d7633775cf44cd49b9e82e9dbba8d19d67bcb467828203b9c" } } ], "extra": [ 1, 44, 96, 112, 192, 73, 84, 230, 90, 110, 31, 208, 177, 167, 232, 23, 173, 231, 71, 16, 164, 226, 165, 86, 228, 110, 118, 204, 161, 46, 222, 72, 58, 2, 17, 0, 0, 0, 14, 122, 156, 244, 199, 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