Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10fb60a0aaccd7b01ed57fa0388dde7ec0917c5ec5b2aaa5dbda446eccbd95bc

Tx prefix hash: 1e44aff28e70ca7b33e9bd68cc672d3903cb9e6ee6a1f75a0782a4cf86a90c94
Tx public key: 98f51e6f23d48e993ebd7d16f58fedd4e820b5371b9516d1eeae61b27e8edfad
Timestamp: 1730412021 Timestamp [UCT]: 2024-10-31 22:00:21 Age [y:d:h:m:s]: 00:027:12:37:09
Block: 1143794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19701 RingCT/type: yes/0
Extra: 0198f51e6f23d48e993ebd7d16f58fedd4e820b5371b9516d1eeae61b27e8edfad021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1656ce1f252c78fb8c95065d73e1c7955e472c1949946dfe91255f0c68034619 0.600000000000 1627787 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": 1143804, "vin": [ { "gen": { "height": 1143794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1656ce1f252c78fb8c95065d73e1c7955e472c1949946dfe91255f0c68034619" } } ], "extra": [ 1, 152, 245, 30, 111, 35, 212, 142, 153, 62, 189, 125, 22, 245, 143, 237, 212, 232, 32, 181, 55, 27, 149, 22, 209, 238, 174, 97, 178, 126, 142, 223, 173, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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