Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e789750f97f6ee4f3355770700ffce0d35b5fd42e7118ecb96530e46271618f

Tx prefix hash: df1547be9e5b8ae2d52c29ac69c58cd9542aa159f89c8052127aac165b3884c9
Tx public key: b2f29d1bcd20020533c63af60bf12c942662be2ade3e0d0b94114072f46b32a7
Timestamp: 1684340495 Timestamp [UCT]: 2023-05-17 16:21:35 Age [y:d:h:m:s]: 02:175:15:43:18
Block: 762169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645351 RingCT/type: yes/0
Extra: 01b2f29d1bcd20020533c63af60bf12c942662be2ade3e0d0b94114072f46b32a702110000000175e3f0e9000000000000000000

1 output(s) for total of 1.830703016000 dcy

stealth address amount amount idx
00: b1df1abccff336bb83d6c9bffab04d4cdce5f57865255c3f8804f0028f46ed3e 1.830703016000 1210888 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": 762179, "vin": [ { "gen": { "height": 762169 } } ], "vout": [ { "amount": 1830703016, "target": { "key": "b1df1abccff336bb83d6c9bffab04d4cdce5f57865255c3f8804f0028f46ed3e" } } ], "extra": [ 1, 178, 242, 157, 27, 205, 32, 2, 5, 51, 198, 58, 246, 11, 241, 44, 148, 38, 98, 190, 42, 222, 62, 13, 11, 148, 17, 64, 114, 244, 107, 50, 167, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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