Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed793781d2b642cc186d697d1cb0db9e39bf0ca96c15818997d520f6a1754ec

Tx prefix hash: 1e4aad7eae79e124b731e800b2d99b42f9e275445f5d39970fea55351990b7b3
Tx public key: 668cee33e06d9464fa0001017c0e4573a35f110f95b0b364da0a8647d60bef68
Timestamp: 1708956625 Timestamp [UCT]: 2024-02-26 14:10:25 Age [y:d:h:m:s]: 01:258:10:33:25
Block: 966007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443439 RingCT/type: yes/0
Extra: 01668cee33e06d9464fa0001017c0e4573a35f110f95b0b364da0a8647d60bef6802110000001c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49f48e277eaaebc8f0e007cd85727aac03b18fc730138574e5b6ddf9ed2d6aa5 0.600000000000 1425764 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": 966017, "vin": [ { "gen": { "height": 966007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49f48e277eaaebc8f0e007cd85727aac03b18fc730138574e5b6ddf9ed2d6aa5" } } ], "extra": [ 1, 102, 140, 238, 51, 224, 109, 148, 100, 250, 0, 1, 1, 124, 14, 69, 115, 163, 95, 17, 15, 149, 176, 179, 100, 218, 10, 134, 71, 214, 11, 239, 104, 2, 17, 0, 0, 0, 28, 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