Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c8035c1937ba14a99ee858cd04880292aa406752c3be47ee5e920f7d5a7b4c

Tx prefix hash: b3cee9e722d712b1c2859ed387270485828760471798e892df46dd5cd1a0011f
Tx public key: 6d7a781df1a67c16f4af6a654712e1c69d1fbc467b9212c808a17381d1222eb7
Timestamp: 1720595485 Timestamp [UCT]: 2024-07-10 07:11:25 Age [y:d:h:m:s]: 01:120:16:51:40
Block: 1062500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344777 RingCT/type: yes/0
Extra: 016d7a781df1a67c16f4af6a654712e1c69d1fbc467b9212c808a17381d1222eb702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 961cbb8b45177ed3968fd63a7fc4974d26ca8c96df44f0e2cf343eab934bdcd8 0.600000000000 1533003 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": 1062510, "vin": [ { "gen": { "height": 1062500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "961cbb8b45177ed3968fd63a7fc4974d26ca8c96df44f0e2cf343eab934bdcd8" } } ], "extra": [ 1, 109, 122, 120, 29, 241, 166, 124, 22, 244, 175, 106, 101, 71, 18, 225, 198, 157, 31, 188, 70, 123, 146, 18, 200, 8, 161, 115, 129, 209, 34, 46, 183, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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