Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e082c22eef20779ed4af47851696b28eef6c91334f629f22deba774254c7aa45

Tx prefix hash: 925f3ab5fe3fbbbc6c93896d7ede4c69c7b3cf05b4739de963ad18ec0a7322fc
Tx public key: b81e9fd0ce690e98e1e9f2ab799b13e7cdc3a0019d8a39e84df29c66c69dd526
Timestamp: 1721523948 Timestamp [UCT]: 2024-07-21 01:05:48 Age [y:d:h:m:s]: 00:217:20:58:45
Block: 1070191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155595 RingCT/type: yes/0
Extra: 01b81e9fd0ce690e98e1e9f2ab799b13e7cdc3a0019d8a39e84df29c66c69dd5260211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b542b08ec25b90aa5d4e4cba58ad871765da070bc07472c1a39acdb87652f46 0.600000000000 1541920 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": 1070201, "vin": [ { "gen": { "height": 1070191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b542b08ec25b90aa5d4e4cba58ad871765da070bc07472c1a39acdb87652f46" } } ], "extra": [ 1, 184, 30, 159, 208, 206, 105, 14, 152, 225, 233, 242, 171, 121, 155, 19, 231, 205, 195, 160, 1, 157, 138, 57, 232, 77, 242, 156, 102, 198, 157, 213, 38, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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