Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1103f498680c36f87b898f73961b2e1d092d6c3bc19abb312943ff854de406ba

Tx prefix hash: 3b35612cfd7e91082419cb4a467a85bf91e040f1c1d4a33d7b17d82e6d4143b4
Tx public key: f0f4cc1e4cd993bbf84de71674bef9418256b7cee5e5c52f030c05c22153a296
Timestamp: 1685161891 Timestamp [UCT]: 2023-05-27 04:31:31 Age [y:d:h:m:s]: 01:342:01:23:24
Block: 768987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505692 RingCT/type: yes/0
Extra: 01f0f4cc1e4cd993bbf84de71674bef9418256b7cee5e5c52f030c05c22153a29602110000000ce6d27f9c000000000000000000

1 output(s) for total of 1.737908961000 dcy

stealth address amount amount idx
00: e7145065571cafd40643857206a9dd7df3405dd5138d0e689e3e9e517a1ef289 1.737908961000 1218218 of 0

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": 768997, "vin": [ { "gen": { "height": 768987 } } ], "vout": [ { "amount": 1737908961, "target": { "key": "e7145065571cafd40643857206a9dd7df3405dd5138d0e689e3e9e517a1ef289" } } ], "extra": [ 1, 240, 244, 204, 30, 76, 217, 147, 187, 248, 77, 231, 22, 116, 190, 249, 65, 130, 86, 183, 206, 229, 229, 197, 47, 3, 12, 5, 194, 33, 83, 162, 150, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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