Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56dc8d0a06f1fd451298e7638198342b8d25b484405b7077a31a6896f99546dc

Tx prefix hash: e9c74c572aade4b3994aa5f90e19d0df643bc076f90d17492afec0a55f138e1b
Tx public key: 8519b1950e8157694482f35730c0b055a8c63a5c765d2e7229eba76458fb2f06
Timestamp: 1716360355 Timestamp [UCT]: 2024-05-22 06:45:55 Age [y:d:h:m:s]: 00:326:23:35:32
Block: 1027391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233720 RingCT/type: yes/0
Extra: 018519b1950e8157694482f35730c0b055a8c63a5c765d2e7229eba76458fb2f06021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e430f8364afca554b96ea8d76826c8e4c814a7ca21699229f6979d1a011d32 0.600000000000 1494982 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": 1027401, "vin": [ { "gen": { "height": 1027391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e430f8364afca554b96ea8d76826c8e4c814a7ca21699229f6979d1a011d32" } } ], "extra": [ 1, 133, 25, 177, 149, 14, 129, 87, 105, 68, 130, 243, 87, 48, 192, 176, 85, 168, 198, 58, 92, 118, 93, 46, 114, 41, 235, 167, 100, 88, 251, 47, 6, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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