Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58df7d303047fb7d4935c9af41b6ee7a826bf29d53ac5abe72338fcac3009f77

Tx prefix hash: 2ecf0d3b4ca4fbd6d8fa956170121f43fe8a47f7dee0ed3cd93189d2187121ef
Tx public key: 62a1c7230bb5f8b0ae3bf727418ed0d9addaab54953b3fe8e97a8c2d29c055d7
Timestamp: 1717247170 Timestamp [UCT]: 2024-06-01 13:06:10 Age [y:d:h:m:s]: 00:321:18:52:01
Block: 1034742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229978 RingCT/type: yes/0
Extra: 0162a1c7230bb5f8b0ae3bf727418ed0d9addaab54953b3fe8e97a8c2d29c055d702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55432907c00d8067c67ad628bc2bfcaeb009400fbfcb0250e9def1c8cf05585a 0.600000000000 1503261 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": 1034752, "vin": [ { "gen": { "height": 1034742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55432907c00d8067c67ad628bc2bfcaeb009400fbfcb0250e9def1c8cf05585a" } } ], "extra": [ 1, 98, 161, 199, 35, 11, 181, 248, 176, 174, 59, 247, 39, 65, 142, 208, 217, 173, 218, 171, 84, 149, 59, 63, 232, 233, 122, 140, 45, 41, 192, 85, 215, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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