Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cdff766c33dd38247e128e66df9dcc29e638fd9e2c81916130fa0513edd6a9c

Tx prefix hash: 03606d9b2f01995c28ffc34b0e042b4a90bdc12837f7303a127c1850b7c18880
Tx public key: eb6011968efd1ec58467e02790a1bd025d3e5ac3e9a29e87a79d6fbca6fec6a5
Timestamp: 1720377749 Timestamp [UCT]: 2024-07-07 18:42:29 Age [y:d:h:m:s]: 00:276:05:25:27
Block: 1060685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197357 RingCT/type: yes/0
Extra: 01eb6011968efd1ec58467e02790a1bd025d3e5ac3e9a29e87a79d6fbca6fec6a5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01f2d539b1fd133b2feb013790d837539e7e1170ae0b0c1232858d1416fe5aa1 0.600000000000 1531170 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": 1060695, "vin": [ { "gen": { "height": 1060685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01f2d539b1fd133b2feb013790d837539e7e1170ae0b0c1232858d1416fe5aa1" } } ], "extra": [ 1, 235, 96, 17, 150, 142, 253, 30, 197, 132, 103, 224, 39, 144, 161, 189, 2, 93, 62, 90, 195, 233, 162, 158, 135, 167, 157, 111, 188, 166, 254, 198, 165, 2, 17, 0, 0, 0, 5, 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