Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d4a5f2d024a657b1ae1e44f7e500238fc9e90fdfa6c5f751efab9741b4f1769

Tx prefix hash: 6cb1654f56062473bd17381cbb5445db8c812a0a7cc9bddabd09c368acb1d45a
Tx public key: d63ab46a00306547bd83a95cbbc31b306a0ff0b86fa60692218fa1a46763272d
Timestamp: 1714371723 Timestamp [UCT]: 2024-04-29 06:22:03 Age [y:d:h:m:s]: 00:342:15:24:03
Block: 1010893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244923 RingCT/type: yes/0
Extra: 01d63ab46a00306547bd83a95cbbc31b306a0ff0b86fa60692218fa1a46763272d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd9862d5dd2b7c6c9b4ba30182b326d433f5b22efda611f14e212fc0111cb9fa 0.600000000000 1472967 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": 1010903, "vin": [ { "gen": { "height": 1010893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd9862d5dd2b7c6c9b4ba30182b326d433f5b22efda611f14e212fc0111cb9fa" } } ], "extra": [ 1, 214, 58, 180, 106, 0, 48, 101, 71, 189, 131, 169, 92, 187, 195, 27, 48, 106, 15, 240, 184, 111, 166, 6, 146, 33, 143, 161, 164, 103, 99, 39, 45, 2, 17, 0, 0, 0, 7, 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